As a depositor with large discrete files, I want to be able to deposit my files as-is without breaking them up, so that the files maintain their integrity.
As a depositor with large files, I want to be warned when a process could take a long time, so that I can decide if my planned method of upload is feasible.
As a depositor with multiple related files, some of which may be large, I want to deposit the files packaged together with information about their relationship (e.g., master data set in native format, a use copy of the same data in an open format, associated metadata files, etc.), so that I can do a one-time deposit of my files packaged together.
As a digital archivist, I want to be able to create a multi-stage workflow that different individuals can access at defined points, so that records creators with a mandate to deposit university records, or the archivist, can initiate a records deposit, records creators or the archivist can add records and metadata, and the archivist can review before final ingest.
As a repository user, I want to nominate a URL for a webpage that has historical significance, so that a digital archivist can review the nomination to determine if it fits the criteria for further ingest into web archiving activities.
As a collection manager, I want to brand my collection, so that it does not look like a generic collection.
As a repository developer, I want to be able to apply custom elements to a collection, so that collections are visually distinct.
As a public user of the repository, I want to have an RSS feed and/or email alerts to monitor new content deposited by author, category, format, keyword, college, so that I know when new content has been deposited.
As a depositor to the repository, I want to have an RSS feed or email alerts widget to re-use (for example, so I can place a feed on my personal website directing users to all instances of my work in the repository), so that I can use a URL for an RSS feed or email alert signup that will work elsewhere.
As a repository user, I want to be able to automatically export the item's citation to a citation management program (e.g., Zotero, RefWorks, EndNote), so that I can capture the citation with one click.
As a repository user, I want to click on a button to generate a citation of the item (a screen that I can then copy and paste from, for example), and choose the citation format (MLA, Turabian, APA, etc.), so that I get a citation viewable on my screen.
As a repository submitter, I want to upload XML documents with TEI encoding, so that: I can display and preserve my TEI encoding.
As a repository user, I want to view documents in a book viewer and turn pages, so that: I don't have to open individual pages of a digitized work (such as a rare book).
As a repository user, I want to allow others to view my .jp2 and .jpx files in an image viewer, so that others can see my files and take advantage JPEG 2000 features such as fast browsing, panning, zooming in/out on image details.
As a repository user, I want to be able to play an audio or video file in the repository, so that I do not have to download something to listen or watch it.
As a repository submitter, I want to be able to format text in the metadata submission fields, so that: I can bold, underline, or italicize text important within the context of my work, and insert URLs where appropriate.
As a repository submitter, I want the file size information to be displayed next to the files associated with my work, so that users are aware of how large files may be.
As a repository user, I want to be able to deep zoom and pan on large, high-resolution images, so that I don't have to download a large image file to be able to zoom or pan.
As a repository submitter, I want to temporarily enable password-based access to a data set, so that another user can download it only when I approve the download.
As a metadata specialist, I want to import metadata in my records into the repository in Dublin Core or Qualified Dublin Core, so that I can do my cataloging in other platforms and import it into the repository without having to crosswalk or map the metadata.
As a metadata specialist, I want to export the metadata in my records in Dublin Core or Qualified Dublin Core, so that I can use the metadata in other platforms and systems that use Dublin Core.
As a metadata specialist, I want to batch import metadata into the repository, so that I can use load multiple metadata records at one time.
As a visual resources librarian, I want to import metadata in my records into the repository in VRA Core 4.0, so that I can do my cataloging in another platform and import it into the repository without having to crosswalk or map the metadata.
As a visual resources librarian, I want to batch import metadata into the repository in XML, so that I can use load multiple metadata records at one time.
As a visual resources librarian, I want to use URIs from the Getty's Art and Architecture Thesaurus (AAT), so that the metadata in my record is linked to the AAT.
As a metadata specialist, I want to make changes to existing fields in multiple metadata records at one time through a batch process (I am making these changes after the records were initially submitted to the repository), so that I can update metadata in multiple records without having to manually make changes in each record.
As a metadata specialist, I want to add new metadata fields and corresponding values to multiple records at one time through a batch process (I am making these changes after the records were initially submitted to the repository), so that I can add new fields and metadata values to multiple records without having to manually make changes in each record.
As a repository submitter, I want to include my ORCID ID in dc.creator or dc.contributor fields, so that my work is connected to my ORCID profile and more easily found.
As a metadata specialist, I want repository users to choose from a list of suggested subject headings for their work in addition to inputting keywords, so that there is more consistent metadata for subject fields that requires less clean-up.
As a repository user, I want to import metadata in my records into the repository in Darwin Core, so that I can reuse my metadata from other subject specific discipline repositories like DRYAD without having to manually re-enter it.
As a metadata specialist, I want to transfer records from MARC to MODS, so that I can use the metadata in library catalog records for digital objects in the digital repository.
As an archivist, I want to export preservation metadata in MODS, so that descriptive metadata in MODS format can be combined with Premis and included with digital objects for long-term preservation.
As a metadata specialist, I want to import metadata records into the repository using a specific metadata schema such as Dublin Core, EAD, MODS, or VRA Core, so that I can do my cataloging in other platforms and import it into the repository without having to crosswalk or map the metadata.
As a metadata specialist, I want to export my metadata records from the repository in a specific metadata schema such as Dublin Core, EAD, MODS, or VRA Core, so that I can use the metadata in other platforms and systems that use those schemas.
As an archivist, I want to import descriptive metadata relating to digital archival collections from EAD Finding Aids, so that I can use descriptive information created in EAD finding aids to describe objects in the digital repository.
As a metadata specialist, I want to use URIs in some fields of my record instead of text strings, so that the metadata in my record is linked to authority records.
As a depositor, I want to be able to create sub-collections within my collection, so that I can organize materials by any sub-grouping I decide.
As a depositor, I want to assign specific collections to a group, so that items in my collection are also part of a group.
As a collection manager, I want to be able to assign hierarchical structures to sub-collections, so that it is clear that my sub-collections are part of a hierarchical group.
As a user of the repository, I want to categorize my items in my collections or groups along parameters I define, such as format, author, or keyword, so that my virtual collection is automatically created with works per the rules I have created (e.g., all of my works tagged with the keyword 'Communism').
As a user of the repository, I want to select specific items I see in the repository for an online exhibit, so that my exhibit may contain works from different depositors, collections, or groups, but it is clear that this is my own assemblage of works from others.
As a collection manager, I want to delegate permission to certain individuals to be able to manage/edit items and metadata for records already in a collection, so that those individuals can login and edit things only where I've given permission.
As a group manager, I want to be able to set permissions for group members, so that I can choose between read-only and editing access for group members.
As a member of a group, I want to see what works I have granted group access to/or others' works I am able to edit, so that I do not have to open an individual item's record to see which groups I have given access to or items which I am able to edit.
As an archivist or collection manager, I want to be notified when any part of a digital object's bitstream changes (from its original checksum), so that I can ensure the fixity of objects in the digital library by comparing any checksum changes.
As an archivist, I want to receive checksum reports for deposited objects and submission information packages, so that I can add this information to our accession reports.
As a repository manager, I want to export digital objects and their metadata as an archival information package at the bit-level, so that I have an exact bit-level copy of the repository objects.
As a repository manager, I want to have old content in the repository scanned for malware, as virus definitions are updated, so that I am certain that the content in the repository doesn't contain any new malware.
As a repository user/journal editor, I want to submit and organize articles in a structure that reflects the organization of journals, so that users can browse my journal in an intuitive manner.
As a user of the repository, I want to do a keyword search for items that match my query and know where in the item that word appears, so that the search results show the contextual placement of the word within the item or its metadata.
As a repository user, I want to search the text of objects within the repository, so that if my search term is contained within the text of an object within the repository, the result will be included in the set of relevant results.
As a metadata professional, I want to get standardized and appropriate information about what is available from the repository, so that I can store that information for my own use or replicate it elsewhere.
As a repository user, I want to perform searches on specified metadata fields, so that I can limit the scope of my search to a single metadata field.
As a repository user, I want to limit my search by a particular facet, so that I can limit an existing search to include only results with a specified, existing heading.
As a repository user, I want to use keyword searching to search every field in all the records, so that I can find stuff related to the terms I'm searching for.
As a repository user, I want to see more relevant results for my keyword search, so that I can find things that are more meaningfully related to my search.
As a metadata specialist, I want to use URIs in some fields of my record instead of text strings, so that the metadata in my record is linked to authority records.
As a repository submitter, I want to filter my search results by subject, discipline, etc., so that I can easily navigate my search results and make them more meaningful.
As a repository user, I want to know what the best link is for sharing with other people, so that I can share a stable URL to other people.
As a repository user, I want to see how search results are being sorted, so that I can better understand the results of my search.
As a repository user, I want to see what other works were created by the creator of a work, so that I can find other works created by a user.
As a repository user, I want to see content before downloading it, so that I can evaluate or read content without downloading it.
As a repository user, I want to search terms to be parsed, so that punctuation and other related forms are treated as white-space or stemmed as appropriate.
As a repository user, I want numerical search terms to be searched, so that I can search for meaningful numerical data, such as Latitude-Longitude geographic subjects.
As a repository user, I want subject results to be clustered, so that results with semantically related subjects are grouped.
As a repository user, I want the search interface to search subject fields, so that search will be improved.
As a repository submitter, I want to see information about file rollback, so that I can understand what it means to rollback a file.
As a repository user, I want to see how big files are, so that I'll know how big a file is before I download it.
As a repository user, I want Scholar to index file names/file titles for keyword searching, so that searching by the file name returns my work in the search results.
As a repository submitter, I want my graduate student proxy submitter to be able to fill out certain fields and other fields to be left blank so I can fill them in (the submission is held in a queue until I can review it), so that I can ensure certain fields are managed by me.
As an archivist, I want it to be clear that a work I am submitting is not necessarily created by me by being able to suppress contributor in the public image, or otherwise make it clear this is an archival submission, so that it is clear who the original publisher/creator is.
As a university records manager, I want university staff members to be able to submit things through a designated page for university records by using their 6+2 and without having to sign up for a DR account, so that submission of university records is more consistent and easier, but university staff submitters do not have control of submissions beyond the initial upload process.
As a university records manager, I want to be able to review and approve for public display the university records submitted by university staff members, so that submission of university records is mediated.
As a submitter to the repository, I want to be able to create "submission templates" that always prepopulate certain fields with boilerplate text of my choosing, so that I can ensure metadata consistency when I am working on large projects with the same provenance/characteristics.
As a visual resources librarian/user/archivist, I want to add a work record (metadata) without adding a digital file, so that I can add a work record to multiple items at a time and add specific information per item later.
As a visual resources librarian/user/archivist, I want to view a submitted batch and view individual records and assign metadata to records I select from one to many, so that I can add metadata to multiple records at a time.
As an archivist, I want to submit large groups of different records at once, so that I can minimize the number of submissions I have to process.
As a collection manager, I want to delegate specific permissions to certain individuals to be able to submit items to some parts of my collection, but not others, so that those individuals can login and upload things only where I've given permission.
As a collection manager, I want to delegate permission to certain individuals to be able to manage/edit items and metadata for records already in a collection, so that those individuals can login and edit things only where I've given permission.
As a repository manager, I want to know when a creator for a record or object is no longer affiliated with the university, so that I am alerted when any logins are no longer associated with someone at the university.
As a repository manager, I want to create an automatic metadata change for objects/metadata deposited by someone who no longer has a UC affiliation, so that when users arrive at a object, they do not send an email to outdated UC contact information.
As a depositor, I want to be able to deposit versions of the same work under the same metadata/catalog record, so that it is clear which version is older/newer.
As a collection manager, I want to delegate specific permissions to certain individuals to be able to submit items to some parts of my collection, but not others, so that those individuals can login and upload things only where I've given permission.
As a repository user, I want to create a permanent DOI to use for sharing and referencing my work, so that regardless of the history of the repository, the same URL will always connect to my work.
As a repository user, I want to restrict certain submissions to on-campus or authenticated UC users, so that I can fulfill restrictions about how content is allowed to be shared.
As a repository user, I want to log into the repository with my UC central login, so that I don't have to create another account, appropriate rights are assigned to my account without having to work with journal staff, and I don't need to manage my account details.
As a repository manager, I want to have new content in the repository scanned for malware, so that I am certain that the content in new submissions is malware free.
As a repository manager, I want to be able to create customized workflows for other users of the repository, so that not all users have to do the same set of steps -- some may be handled by me.
As a repository manager, I want to be able to identify broken HTML links in metadata, so that I can decide whether to remove or redirect broken links.
As a repository submitter, I want to be able to upload a video, so that my content will be viewable.
As a repository submitter, I want a glossary to explain collection, group, etc., so that I will understand the terms and choose the correct option for my work.
As a repository submitter, I want a list of acceptable file formats for each work type, so that I know if my file will upload successfully.
As a repository submitter, I want a list of maximum file sizes, so that I know if my file will upload successfully.
As a repository submitter, I want to assign a thumbnail image for my work when I upload files (especially for video), so that I can choose the thumbnail image that displays to users when they search.
As a repository submitter, I want to be able to reuse metadata from my previous submissions to  populate my current input form, so that I don't have to manually re-enter identical metadata on multiple input forms for works that are very similar.
As a repository submitter, I want to batch upload multiples files and associated metadata, including connections through cloud storage (Google Drive, Dropbox, Box), so that I don't have to manually upload multiples files and re-enter similar metadata.
As a repository submitter, I want to copy/paste my abstract from another source into the input form and have the original formatting transfer, so that my abstract has consistent formatting across platforms.
As a repository submitter, I want to change the typescript of my metadata record, so that I can customize the appearance of my metadata.
As a repository submitter, I want to use italics in my metadata record, so that I can use italics when I need to (such as for scientific names).
As a repository submitter, I want to use diacritics or special characters in my metadata record, so that I can correctly input symbols, foreign language names and words in my record.
As a repository submitter, I want to use an RIS (bibliographic software interchange file format) file and upload article citation information from Zotero, so that I don't have to re-enter metadata and my metadata will be consistent across platforms.
As a repository submitter, I want the input form to visually flag which specific fields need to be filled out if I submit an incomplete record, so that I don't have to click on each field to see if it is required.
As a repository submitter, I want a warning that I should close out any open files before hitting submit, so that I upload the appropriate documents for my work.
As a repository submitter, I want an indicator that the system is "thinking" and the upload is still in progress, so that I know the status of the upload of my content.
As a repository submitter, I want the SHERPA ROMEO link to open in a new window, so that I won't lose data entered in the submission form fields if I press the back button on the current window.
As a repository user, I want to know that when I update/change my password that it should be 8 characters long before I click 'Update Account', so that I do not enter in a password that is less than the required length.
As a repository user, I want to stay on profile page after updating password, so that I can make more changes to my profile.
As a repository user, I want to click a 'Log Out' button instead of navigating to my name and clicking 'Log Out', so that it is easier to find and faster to log out.
As a repository user, I want the title field to auto-populate with my file name after attaching an additional file to an existing record/work, so that I do not accidentally upload an additional file to my work without some kind of title.
As a repository user, I want to change my file name at the time of initial creation of a work, so that I do not have to go back and edit the file name later.
As a repository user, I want to make my submission private but delegate permission to view my work to any specific individual, so that I can share my work with a small audience until the item is ready for greater access.
As a repository user, I want to clearly identify the file-upload dialog, so that I don't accidentally submit a work without attaching a file.
As a repository user, I want to batch upload and preserve parent-child folder structure without submitting a zip file, so that I can preserve relationships between files within the work.
As a delegate, I want the 'My works' page to clearly distinguish between my own authored works, and works I submit on behalf of others, so that 'My works' page shows the works I authored.
As a submitter, I want to control what fields others can edit who have access to my work, so that not all people who have access to my work can edit all of the fields.
As a repository submitter, I want to have the option of providing a title and/or a description when I add or edit an external link, so that users will know what the link is and how it relates to the work they're viewing.
As a repository submitter, I want to see what my delegates are doing on my behalf, so that I can easily hold delegates accountable for their work on my behalf.
As a repository user, I want to see a mention and/or link to the university's intellectual property policies, so that I understand how the legal language in the digital repository fit in with the larger university intellectual property policies.
As a repository user, I want guidance on whether my copyrighted materials can be placed in the repository, so that I can still preserve my own copyrighted materials.
As a repository user, I want to enter the journal title in which my work was originally published, so that I know whether I may deposit my copyrighted or previously published work.
As a repository user, I want a "plain English" summary of the distribution license, so that I can get the highlights.
As a repository user, I want to have better subject headings in the distribution license, so that I can read the sections that most pertain to my concerns.
As a repository user, I want to be alerted when the terms of use and distribution license change, so that I do not have to seek out these changes on my own.
As a repository user, I want to understand what would happen if UC's digital repository shut down, so that I do not have to worry my material might disappear one day.
As a repository user, I want to be able to easily find the distribution license I saw when I submitted content, so that I can review the distribution content.
As a repository user, I want to have my embargoed content go public once my article is published, so that my content in the repository is not available before the official date of publication in another venue.
As a repository user, I want to fill out a survey/use a tool to determine the Creative Commons license that fits my needs, so that I choose the right type of license appropriate to my content and expectations.
As a repository user, I want to assign different rights to different files associated with my work, so that not all of my files associated with a work have the same level of rights.
As a repository contributor, I want to see how many times my content has been accessed, so that I can see how much my content is being used, and share that information with other users, if desired.
As a repository contributor, I want to receive reports on how many times my content has been accessed, so that I can keep track of how much my content is being used, and share that information with other users, if desired.
As a repository manager, I want to get reports about object creation, object page views, content downloads, and search activity, so that I can see how much the repository is being used.
As a developer, I want to be able to develop applications against the Curate repository, so that I can develop more tailored applications to ingest and manipulate objects and metadata in the repository.
As a repository submitter, I want my content to be discoverable through Google Scholar, so that my work reaches more audiences.